After PR

Bumps minor version to 0.22.0

Currently, if a customer's BE hits a PropelAuth rate limit, this library converts the response into

Result::Err(SomeRequestSpecificError::UnexpectedException)

After this change, these responses will instead be converted to

Result::Err(SomeRequestSpecificError::PropelAuthRateLimit)

Note

All validate*_api_key methods perform additional parsing on the error body in the case of a 429 to distinguish between rate limits set by customers to be enforced on end-users – ie the recently added

ApiKeyValidationErrorResponse::EndUserApiKeyRateLimited{ ... }

and rate limits set and imposed by PropelAuth – ie the new

SomeRequestSpecificError::PropelAuthRateLimit

Test

1. Setup a local dev environment with a rate limit on the hostname of 5 request / 10 seconds and a rate limit of 10 requests / 1 minute on personal api keys.
2. Spammed an example app with w/ a personal api key
3. validated the example app's responses could differentiate between when the PropelAuth rate limit was hit and and when the personal-api-key rate limit was hit. The detailed error message data was still successfully parsed and returned in the case of an end-user rate limit being hit.